API

Finance APIs

PUT finance/general-ledger/{generalLedgerPostingId}

Saves information about general ledger posting

HTTP method PUT
URI https://api.rambase.net/finance/general-ledger/{generalLedgerPostingId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {generalLedgerPostingId} General ledger posting identifier
Integer, minimum 100000
Custom fields Custom fields supported
Successful HTTP status code 200
API resource identifier 5289, version 4

The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.

Format:
1
<GeneralLedgerPosting
GeneralLedgerPosting

This field is optional.

>
2
     <AccountingPeriod
AccountingPeriod

This field is optional.

>
3
          <AccountingPeriodId
AccountingPeriodId

Accounting period identifier

Minimum value: 190000

Maximum value: 290000

This field is optional.

>
{Integer}</AccountingPeriodId>
4
     </AccountingPeriod>
5
     <TransactionDate
TransactionDate

Transaction date of general ledger posting

This field is optional.

>
{Date}</TransactionDate>
6
     <Note
Note

Remark of the general ledger posting

This field is optional.

>
{String}</Note>
7
</GeneralLedgerPosting>
1
{
2
     "generalLedgerPosting
GeneralLedgerPosting

This field is optional.

":
{
3
          "accountingPeriod
AccountingPeriod

This field is optional.

":
{
4
               "accountingPeriodId
AccountingPeriodId

Accounting period identifier

Minimum value: 190000

Maximum value: 290000

This field is optional.

":
"{Integer}"
5
          },
6
          "transactionDate
TransactionDate

Transaction date of general ledger posting

This field is optional.

":
"{Date}",
7
          "note
Note

Remark of the general ledger posting

This field is optional.

":
"{String}"
8
     }
9
}

The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.

$access_token String, optional After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time.
$db String, optional Set the database/company for the request
$useMinimumVersion Integer, optional Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information.
$showCustomFields Boolean, optional Set to "true" to include custom fields. Default value is false.

Read more about filters and sorting on how to use filter parameters and named filters.

Read more about filters and sorting on how to use sortable parameters

Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields. Fields colored in grey is expandable fields.

Please note that some fields may be removed from the response, based on user roles/duties/permissions.

Format:
1
1

List of available operations/actions for this resource.
See the operations documentation for more information about API operations.

Possible error codes the response might return:

Error 105127 HTTP 400 Accounting period {0} already exists.
Error 105128 HTTP 400 Invalid Type value.
Error 100511 HTTP 400 Invalid date
Error 105129 HTTP 400 Start date cannot be greater than end date.
Error 105130 HTTP 400 Both dates or no dates must be provided.
Error 105288 HTTP 400 StartDate and EndDate must be provided when creating accounting periods manually.